SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Cold boot attack</title>

</head>

Cold boot attack

</h1>

</header>

In <a href="Computer_security" title="Computer security">computer security</a>, a cold boot attack (or to a lesser extent, a platform reset attack) is a type of <a href="Side_channel_attack" class="mw-redirect" title="Side channel attack">side channel attack</a> in which an attacker with <a href="Physical_access" title="Physical access">physical access</a> to a computer performs a <a href="Memory_dump" class="mw-redirect" title="Memory dump">memory dump</a> of a computer's <a href="Random-access_memory" title="Random-access memory">random-access memory (RAM)</a> by performing a hard reset of the target machine. Typically, cold boot attacks are used for retrieving encryption <a href="Key_(cryptography)" title="Key (cryptography)">keys</a> from a running <a href="Operating_system" title="Operating system">operating system</a> for malicious or criminal investigative reasons.<a href="#cite_note-MacIver2006-1">[1]</a><a href="#cite_note-halderman2008-2">[2]</a><a href="#cite_note-forensic2011-3">[3]</a> The attack relies on the <a href="Data_remanence" title="Data remanence">data remanence</a> property of <a href="Dynamic_random-access_memory" title="Dynamic random-access memory">DRAM</a> and <a href="Static_random-access_memory" title="Static random-access memory">SRAM</a> to retrieve memory contents that <a href="DRAM_data_remanence" class="mw-redirect" title="DRAM data remanence">remain readable</a> in the seconds to minutes following a power switch-off.<a href="#cite_note-halderman2008-2">[2]</a><a href="#cite_note-skorobogatov2002-4">[4]</a><a href="#cite_note-bitlocker2008-5">[5]</a>

An attacker with physical access to a running computer typically executes a cold boot attack by <a href="Cold-booting" class="mw-redirect" title="Cold-booting">cold-booting</a> the machine and booting a lightweight operating system from a removable disk to dump the contents of pre-boot physical <a href="Random-access_memory" title="Random-access memory">memory</a> to a file.<a href="#cite_note-memTool2008-6">[6]</a><a href="#cite_note-halderman2008-2">[2]</a> An attacker is then free to analyze the data <a href="Core_dump" title="Core dump">dumped</a> from memory to find sensitive data, such as the <a href="Key_(cryptography)" title="Key (cryptography)">keys</a>, using various forms of <a href="Key_finding_attacks" title="Key finding attacks">key finding attacks</a>.<a href="#cite_note-7">[7]</a><a href="#cite_note-hargreaves2008-8">[8]</a> Since cold boot attacks target <a href="Random-access_memory" title="Random-access memory">random-access memory</a>, <a href="Full_disk_encryption" class="mw-redirect" title="Full disk encryption">full disk encryption</a> schemes, even with a <a href="Trusted_platform_module" class="mw-redirect" title="Trusted platform module">trusted platform module</a> installed are ineffective against this kind of attack.<a href="#cite_note-halderman2008-2">[2]</a> This is because the problem is fundamentally a <a href="Computer_hardware" title="Computer hardware">hardware</a> (insecure memory) and not a <a href="Software" title="Software">software</a> issue. However, malicious access can be prevented by limiting physical access and using modern techniques to avoid storing sensitive data in <a href="Random-access_memory" title="Random-access memory">random-access memory</a>.

<div class="mw-heading mw-heading2"><h2 id="Technical_details">Technical details</h2></div>

<a href="DIMM" title="DIMM">DIMM memory modules</a> gradually lose data over time as they lose power, but do not immediately lose all data when power is lost.<a href="#cite_note-halderman2008-2">[2]</a> With certain memory modules, the time window for an attack can be extended to hours or even a week by cooling them with <a href="Freeze_spray" title="Freeze spray">freeze spray</a> and liquid nitrogen. Furthermore, as the <a href="Bit" title="Bit">bits</a> disappear in memory over time, they can be reconstructed, as they fade away in a predictable manner.<a href="#cite_note-halderman2008-2">[2]</a> Consequently, an attacker can perform a <a href="Memory_dump" class="mw-redirect" title="Memory dump">memory dump</a> of its contents by executing a cold boot attack. The ability to execute the cold boot attack successfully varies considerably across different systems, types of memory, memory manufacturers and motherboard properties, and may be more difficult to carry out than software-based methods or a <a href="DMA_attack" title="DMA attack">DMA attack</a>.<a href="#cite_note-carbone2011-9">[9]</a> While the focus of current research is on disk encryption, any sensitive data held in memory is vulnerable to the attack.<a href="#cite_note-halderman2008-2">[2]</a>

Attackers execute cold boot attacks by forcefully and abruptly rebooting a target machine and then booting a pre-installed operating system from a <a href="USB_flash_drive" title="USB flash drive">USB flash drive</a>, <a href="CD-ROM" title="CD-ROM">CD-ROM</a> or <a href="Network_boot" class="mw-redirect" title="Network boot">over the network</a>.<a href="#cite_note-forensic2011-3">[3]</a> In cases where it is not practical to hard reset the target machine, an attacker may alternatively physically remove the <a href="DIMM" title="DIMM">memory modules</a> from the original system and quickly place them into a compatible machine under the attacker's control, which is then booted to access the memory.<a href="#cite_note-halderman2008-2">[2]</a> Further analysis can then be performed against the data dumped from <a href="Random-access_memory" title="Random-access memory">RAM</a>.

A similar kind of attack can also be used to extract data from memory, such as a <a href="DMA_attack" title="DMA attack">DMA attack</a> that allows the physical memory to be accessed via a high-speed expansion port such as <a href="FireWire" class="mw-redirect" title="FireWire">FireWire</a>.<a href="#cite_note-forensic2011-3">[3]</a> A cold boot attack may be preferred in certain cases, such as when there is high risk of hardware damage. Using the high-speed expansion port can <a href="Short_circuit" title="Short circuit">short out</a>, or physically damage hardware in certain cases.<a href="#cite_note-forensic2011-3">[3]</a>

Cold boots attacks are typically used for <a href="Digital_forensics" title="Digital forensics">digital forensic investigations</a>, malicious purposes such as theft and data recovery, although just having fun cannot be ruled out.<a href="#cite_note-forensic2011-3">[3]</a>

<div class="mw-heading mw-heading3"><h3 id="Digital_forensics">Digital forensics</h3></div>

In certain cases, a cold boot attack is used in the discipline of <a href="Digital_forensics" title="Digital forensics">digital forensics</a> to forensically preserve data contained within memory as criminal evidence.<a href="#cite_note-forensic2011-3">[3]</a> For example, when it is not practical to preserve data in memory through other means, a cold boot attack may be used to perform a dump of the data contained in <a href="Random-access_memory" title="Random-access memory">random-access memory</a>. For example, a cold boot attack is used in situations where a system is secured and it is not possible to access the computer.<a href="#cite_note-forensic2011-3">[3]</a> A cold boot attack may also be necessary when a hard disk is encrypted with <a href="Full_disk_encryption" class="mw-redirect" title="Full disk encryption">full disk encryption</a> and the disk potentially contains evidence of criminal activity. A cold boot attack provides access to the memory, which can provide information about the state of the system at the time such as what programs are running.<a href="#cite_note-forensic2011-3">[3]</a>

<div class="mw-heading mw-heading3"><h3 id="Malicious_intent">Malicious intent</h3></div>

A cold boot attack may be used by attackers to gain access to encrypted information such as financial information or <a href="Trade_secret" title="Trade secret">trade secrets</a> for malicious intent.<a href="#cite_note-gruhn2016-10">[10]</a>

<div class="mw-heading mw-heading2"><h2 id="Circumventing_full_disk_encryption">Circumventing full disk encryption</h2></div>

A common purpose of cold boot attacks is to circumvent software-based disk encryption. Cold boot attacks when used in conjunction with <a href="Key_finding_attacks" title="Key finding attacks">key finding attacks</a> have been demonstrated to be an effective means of circumventing <a href="Full_disk_encryption" class="mw-redirect" title="Full disk encryption">full disk encryption</a> schemes of various vendors and <a href="Operating_system" title="Operating system">operating systems</a>, even where a <a href="Trusted_Platform_Module" title="Trusted Platform Module">Trusted Platform Module</a> (TPM) <a href="Secure_cryptoprocessor" title="Secure cryptoprocessor">secure cryptoprocessor</a> is used.<a href="#cite_note-halderman2008-2">[2]</a>

In the case of disk encryption applications that can be configured to allow the operating system to boot without a pre-<a href="Booting" title="Booting">boot</a> <a href="Personal_identification_number" title="Personal identification number">PIN</a> being entered or a hardware key being present (e.g. <a href="BitLocker" title="BitLocker">BitLocker</a> in a simple configuration that uses a TPM without a <a href="Two-factor_authentication" class="mw-redirect" title="Two-factor authentication">two-factor authentication</a> PIN or USB key), the time frame for the attack is not limiting at all.<a href="#cite_note-halderman2008-2">[2]</a>

<div class="mw-heading mw-heading3"><h3 id="BitLocker">BitLocker</h3></div>

<a href="BitLocker" title="BitLocker">BitLocker</a> in its default configuration uses a <a href="Trusted_platform_module" class="mw-redirect" title="Trusted platform module">trusted platform module</a> that neither requires a <a href="Personal_identification_number" title="Personal identification number">PIN</a>, nor an external key to decrypt the disk. When the <a href="Operating_system" title="Operating system">operating system</a> boots, <a href="BitLocker" title="BitLocker">BitLocker</a> retrieves the key from the TPM, without any user interaction. Consequently, an attacker can simply power on the machine, wait for the operating system to begin <a href="Booting" title="Booting">booting</a> and then execute a cold boot attack against the machine to retrieve the key. Due to this, <a href="Two-factor_authentication" class="mw-redirect" title="Two-factor authentication">two-factor authentication</a>, such as a pre-boot PIN or a removable USB device containing a startup key together with a TPM should be used to work around this vulnerability in the default BitLocker implementation.<a href="#cite_note-bitlockerOverview2008-11">[11]</a><a href="#cite_note-bitlocker2008-5">[5]</a> However, this workaround only prevents a cold boot attack if the machine was off before the attacker gained physical access. If the machine had already booted and is running, it does not prevent an attacker from retrieving sensitive data from memory, nor from retrieving encryption keys cached in memory.

<div class="mw-heading mw-heading3"><h3 id="Mitigation">Mitigation</h3></div>

Since a <a href="Memory_dump" class="mw-redirect" title="Memory dump">memory dump</a> can be easily performed by executing a cold boot attack, storage of sensitive data in RAM, like encryption keys for <a href="Full_disk_encryption" class="mw-redirect" title="Full disk encryption">full disk encryption</a> is unsafe. Several solutions have been proposed for storing encryption keys in areas, other than <a href="Random-access_memory" title="Random-access memory">random-access memory</a>. While these solutions may reduce the chance of breaking full disk encryption, they provide no protection of other sensitive data stored in memory.

<div class="mw-heading mw-heading4"><h4 id="Register-based_key_storage">Register-based key storage</h4></div>

One solution for keeping encryption keys out of memory is register-based key storage. Implementations of this solution are <a href="TRESOR" title="TRESOR">TRESOR</a><a href="#cite_note-tresor-usenix-12">[12]</a> and Loop-Amnesia.<a href="#cite_note-loopamnesia-acsac-13">[13]</a> Both of these implementations modify the <a href="Kernel_(operating_system)" title="Kernel (operating system)">kernel</a> of an operating system so that <a href="CPU_register" class="mw-redirect" title="CPU register">CPU registers</a> (in TRESOR's case the <a href="X86_debug_register" title="X86 debug register">x86 debug registers</a> and in Loop-Amnesia's case the AMD64 or EMT64 profiling registers) can be used to store encryption keys, rather than in RAM. Keys stored at this level cannot easily be read from <a href="User_space" class="mw-redirect" title="User space">userspace</a> and are lost when the computer restarts for any reason. TRESOR and Loop-Amnesia both must use on-the-fly <a href="Key_schedule" title="Key schedule">round key</a> generation due to the limited space available for storing cryptographic tokens in this manner. For security, both disable interrupts to prevent key information from leaking to memory from the CPU registers while encryption or decryption is being performed, and both block access to the debug or profile registers.

There are two potential areas in modern <a href="X86" title="X86">x86</a> processors for storing keys: the <a href="Streaming_SIMD_Extensions" title="Streaming SIMD Extensions">SSE</a> registers which could in effect be made privileged by disabling all SSE instructions (and necessarily, any programs relying on them), and the debug registers which were much smaller but had no such issues.

A <a href="Proof_of_concept" title="Proof of concept">proof of concept</a> distribution called 'paranoix' based on the SSE register method has been developed.<a href="#cite_note-muller2010-14">[14]</a> The developers claim that "running TRESOR on a 64-bit CPU that supports <a href="AES-NI" class="mw-redirect" title="AES-NI">AES-NI</a>, there is no performance penalty compared to a generic implementation of <a href="Advanced_Encryption_Standard" title="Advanced Encryption Standard">AES</a>",<a href="#cite_note-tresorBlog-15">[15]</a> and run slightly faster than standard encryption despite the need for key recalculation.<a href="#cite_note-tresor-usenix-12">[12]</a> The primary advantage of Loop-Amnesia compared to TRESOR is that it supports the use of multiple encrypted drives; the primary disadvantages are a lack of support for 32-bit x86 and worse performance on CPUs not supporting AES-NI.

<div class="mw-heading mw-heading4"><h4 id="Cache-based_key_storage">Cache-based key storage</h4></div>

"Frozen cache" (sometimes known as "cache as RAM"),<a href="#cite_note-tews2010-16">[16]</a> may be used to securely store encryption keys. It works by disabling a CPU's L1 cache and uses it for key storage, however, this may significantly degrade overall system performance to the point of being too slow for most purposes.<a href="#cite_note-frozencache-17">[17]</a>

A similar cache-based solution was proposed by Guan et al. (2015)<a href="#cite_note-copker-18">[18]</a> by employing the WB (Write-Back) cache mode to keep data in caches, reducing the computation times of public key algorithms.

Mimosa<a href="#cite_note-guan2015-19">[19]</a> in IEEE S&P 2015 presented a more practical solution for public-key cryptographic computations against cold-boot attacks and DMA attacks. It employs hardware transactional memory (HTM) which was originally proposed as a speculative memory access mechanism to boost the performance of multi-threaded applications. The strong atomicity guarantee provided by HTM, is utilized to defeat illegal concurrent accesses to the memory space that contains sensitive data. The RSA private key is encrypted in memory by an AES key that is protected by TRESOR. On request, an RSA private-key computation is conducted within an HTM transaction: the private key is firstly decrypted into memory, and then RSA decryption or signing is conducted. Because a plain-text RSA private key only appears as modified data in an HTM transaction, any read operation to these data will abort the transaction - the transaction will roll-back to its initial state. Note that, the RSA private key is encrypted in initial state, and it is a result of write operations (or AES decryption). Currently HTM is implemented in caches or store-buffers, both of which are located in CPUs, not in external RAM chips. So cold-boot attacks are prevented. Mimosa defeats against attacks that attempt to read sensitive data from memory (including cold-boot attacks, DMA attacks, and other software attacks), and it only introduces a small performance overhead.

<div class="mw-heading mw-heading4"><h4 id="Dismounting_encrypted_disks">Dismounting encrypted disks</h4></div>

Best practice recommends dismounting any encrypted, non-system disks when not in use, since most disk encryption software are designed to securely erase keys cached in memory after use.<a href="#cite_note-dean2009-20">[20]</a> This reduces the risk of an attacker being able to salvage encryption keys from memory by executing a cold boot attack. To minimize access to encrypted information on the operating system hard disk, the machine should be completely shut down when not in use to reduce the likelihood of a successful cold boot attack.<a href="#cite_note-halderman2008-2">[2]</a><a href="#cite_note-wired2008-21">[21]</a> However, <a href="Data_remanence" title="Data remanence">data may remain readable</a> from tens of seconds to several minutes depending upon the physical RAM device in the machine, potentially allowing some data to be retrieved from memory by an attacker. Configuring an <a href="Operating_system" title="Operating system">operating system</a> to shut down or hibernate when unused, instead of using sleep mode, can help mitigate the risk of a successful cold boot attack.

<div class="mw-heading mw-heading2"><h2 id="Effective_countermeasures">Effective countermeasures</h2></div>

<div class="mw-heading mw-heading3"><h3 id="Preventing_physical_access">Preventing physical access</h3></div>

Typically, a cold boot attack can be prevented by limiting an attacker's <a href="Physical_access" title="Physical access">physical access</a> to the computer or by making it increasingly difficult to carry out the attack. One method involves <a href="Soldering" title="Soldering">soldering</a> or gluing in the <a href="DIMM" title="DIMM">memory modules</a> onto the <a href="Motherboard" title="Motherboard">motherboard</a>, so they cannot be easily removed from their sockets and inserted into another machine under an attacker's control.<a href="#cite_note-halderman2008-2">[2]</a> However, this does not prevent an attacker from booting the victim's machine and performing a <a href="Memory_dump" class="mw-redirect" title="Memory dump">memory dump</a> using a removable <a href="USB_flash_drive" title="USB flash drive">USB flash drive</a>. A <a href="Vulnerability_mitigation" class="mw-redirect" title="Vulnerability mitigation">mitigation</a> such as <a href="UEFI_Secure_Boot" class="mw-redirect" title="UEFI Secure Boot">UEFI Secure Boot</a> or similar boot verification approaches can be effective in preventing an attacker from booting up a custom software environment to dump out the contents of soldered-on main memory.<a href="#cite_note-weis-22">[22]</a>

<div class="mw-heading mw-heading3"><h3 id="Full_memory_encryption">Full memory encryption</h3></div>

Encrypting <a href="Random-access_memory" title="Random-access memory">random-access memory</a> (RAM) mitigates the possibility of an attacker being able to obtain <a href="Key_(cryptography)" title="Key (cryptography)">encryption keys</a> or other material from memory via a cold boot attack. This approach may require changes to the operating system, applications, or hardware. One example of hardware-based memory encryption was implemented in the <a href="Microsoft" title="Microsoft">Microsoft</a> <a href="Xbox_(console)" title="Xbox (console)">Xbox</a>.<a href="#cite_note-23">[23]</a> Implementations on newer x86-64 hardware are available from AMD and on Intel <a href="Willow_Cove" title="Willow Cove">Willow Cove</a> and newer.

Software-based full memory encryption is similar to CPU-based key storage since key material is never exposed to memory, but is more comprehensive since all memory contents are encrypted. In general, only immediate pages are decrypted and read on the fly by the operating system.<a href="#cite_note-ramCrypt2016-24">[24]</a> Implementations of software-based memory encryption solutions include: a commercial product from <a href="PrivateCore" title="PrivateCore">PrivateCore</a>.<a href="#cite_note-25">[25]</a><a href="#cite_note-26">[26]</a><a href="#cite_note-27">[27]</a> and RamCrypt, a kernel-patch for the Linux kernel that encrypts data in memory and stores the encryption key in the CPU registers in a manner similar to <a href="TRESOR" title="TRESOR">TRESOR</a>.<a href="#cite_note-tresor-usenix-12">[12]</a><a href="#cite_note-ramCrypt2016-24">[24]</a>

Since version 1.24, <a href="VeraCrypt" title="VeraCrypt">VeraCrypt</a> supports RAM encryption for keys and passwords.<a href="#cite_note-28">[28]</a>

More recently, several papers have been published highlighting the availability of security-enhanced x86 and ARM commodity processors.<a href="#cite_note-29">[29]</a><a href="#cite_note-30">[30]</a> In that work, an ARM Cortex A8 processor is used as the substrate on which a full memory encryption solution is built. Process segments (for example, stack, code or heap) can be encrypted individually or in composition. This work marks the first full memory encryption implementation on a general-purpose commodity processor. The system provides both confidentiality and integrity protections of code and data which are encrypted everywhere outside the CPU boundary.

<div class="mw-heading mw-heading3"><h3 id="Secure_erasure_of_memory">Secure erasure of memory</h3></div>

Since cold boot attacks target unencrypted <a href="Random-access_memory" title="Random-access memory">random-access memory</a>, one solution is to erase sensitive data from memory when it is no longer in use. The "TCG Platform Reset Attack Mitigation Specification",<a href="#cite_note-31">[31]</a> an industry response to this specific attack, forces the <a href="BIOS" title="BIOS">BIOS</a> to overwrite memory during <a href="Power-on_self-test" title="Power-on self-test">POST</a> if the operating system was not shut down cleanly. However, this measure can still be circumvented by removing the memory module from the system and reading it back on another system under the attacker's control that does not support these measures.<a href="#cite_note-halderman2008-2">[2]</a>

An effective secure erase feature would be that if power is interrupted, the RAM is wiped in the less than 300 ms before power is lost in conjunction with a secure BIOS and hard drive/SSD controller that encrypts data on the M-2 and SATAx ports. If the <a href="RAM" class="mw-redirect" title="RAM">RAM</a> itself contained no serial presence or other data and the timings were stored in the BIOS with some form of failsafe requiring a hardware key to change them, it would be nearly impossible to recover any data and would also be immune to <a href="Tempest_(codename)" title="Tempest (codename)">TEMPEST</a> attacks, man-in-the-RAM and other possible infiltration methods.<a href="#cite_note-32">[32]</a>

Some <a href="Operating_systems" class="mw-redirect" title="Operating systems">operating systems</a> such as <a href="Tails_(operating_system)" title="Tails (operating system)">Tails</a> provide a feature that securely writes random data to system memory when the operating system is shut down to mitigate against a cold boot attack.<a href="#cite_note-tails-33">[33]</a> However, video memory erasure is still not possible and as of 2022 it's still an open ticket on the Tails forum.<a href="#cite_note-34">[34]</a> Potential attacks which could exploit this flaw are:

<ul><li>Generation of a <a href="GNU_Privacy_Guard" title="GNU Privacy Guard">GnuPG keypair</a> and viewing the private key on a text editor could lead to the key being recovered.<a href="#cite_note-35">[35]</a></li>

<li>A <a href="Cryptocurrency" title="Cryptocurrency">cryptocurrency</a> seed could be seen, therefore bypassing the wallet (even if encrypted) allowing access to the funds.</li>

<li>Typing a password with visibility enabled might show parts of it or even the whole key. If a keyfile is used, it could be shown to reduce time needed for a password attack.</li>

<li>Traces of mounted or opened encrypted volumes with <a href="Plausible_deniability" title="Plausible deniability">plausible deniability</a> might be shown, leading to the discovery of them.</li>

<li>If connected to a <a href=".onion" title=".onion">.onion</a> service, the <a href="URL" title="URL">URL</a> might be shown and lead to its discovery, whereas otherwise would be extremely difficult.<a href="#cite_note-36">[36]</a><a href="#cite_note-37">[37]</a></li>

<li>Usage of a particular program could show user's patterns. For instance, if a <a href="Steganography" title="Steganography">steganography</a> program is used and opened, the assumption that the user has been hiding data could be made. Likewise, if an instant messenger is being used, a list of contacts or messages could be shown.</li></ul>

<div class="mw-heading mw-heading3"><h3 id="External_key_storage">External key storage</h3></div>

A cold boot attack can be prevented by ensuring no keys are stored by the hardware under attack.

<ul><li>User enters the disk encryption key manually</li>

<li>Using an <a href="Hardware-based_full_disk_encryption#Enclosed_hard_disk_drive_FDE" title="Hardware-based full disk encryption">enclosed fully encrypted hard disk drive</a> where the <a href="Key_(cryptography)" title="Key (cryptography)">encryption keys</a> are held in hardware separate from the <a href="Hard_disk_drive" title="Hard disk drive">hard disk drive</a>.</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Ineffective_countermeasures">Ineffective countermeasures</h2></div>

<a href="Memory_scrambling" class="mw-redirect" title="Memory scrambling">Memory scrambling</a> may be used to minimize undesirable parasitic effects of semiconductors as a feature of modern <a href="Intel_Core" title="Intel Core">Intel Core</a> processors.<a href="#cite_note-38">[38]</a><a href="#cite_note-39">[39]</a><a href="#cite_note-40">[40]</a><a href="#cite_note-41">[41]</a>

However, because the scrambling is only used to <a href="Decorrelation" title="Decorrelation">decorrelate</a> any patterns within the memory contents, the memory can be descrambled via a descrambling attack.<a href="#cite_note-42">[42]</a><a href="#cite_note-43">[43]</a> Hence, memory scrambling is not a viable mitigation against cold boot attacks.

<a href="Hibernate_(OS_feature)" class="mw-redirect" title="Hibernate (OS feature)">Sleep mode</a> provides no additional protection against a cold boot attack because data typically still resides in memory while in this state. As such, full disk encryption products are still vulnerable to attack because the keys reside in memory and do not need to be re-entered once the machine resumes from a low power state.

Although limiting the boot device options in the <a href="BIOS" title="BIOS">BIOS</a> may make it slightly harder to boot another operating system, firmware in modern chipsets tends to allow the user to override the boot device during <a href="Power-on_self_test" class="mw-redirect" title="Power-on self test">POST</a> by pressing a specified hot key.<a href="#cite_note-bitlocker2008-5">[5]</a><a href="#cite_note-microsoftBios2018-44">[44]</a><a href="#cite_note-biosKeys-45">[45]</a> Limiting the boot device options will not prevent the memory module from being removed from the system and read back on an alternative system either. In addition, most chipsets provide a recovery mechanism that allows the BIOS settings to be reset to default even if they are protected with a password.<a href="#cite_note-gruhn2016-10">[10]</a><a href="#cite_note-dell-46">[46]</a> The <a href="BIOS" title="BIOS">BIOS settings</a> can also be modified while the system is running to circumvent any protections enforced by it, such as memory wiping or locking the boot device.<a href="#cite_note-47">[47]</a><a href="#cite_note-48">[48]</a><a href="#cite_note-49">[49]</a>

<div class="mw-heading mw-heading2"><h2 id="Smartphones">Smartphones</h2></div>

The cold boot attack can be adapted and carried out in a similar manner on Android <a href="Smartphone" title="Smartphone">smartphones</a>.<a href="#cite_note-cellPhones2018-50">[50]</a> A cold boot can be performed by disconnecting the phone's battery to force a hard reset or holding down the power button.<a href="#cite_note-cellPhones2018-50">[50]</a> The smartphone is then flashed with an operating system image that can perform a <a href="Memory_dump" class="mw-redirect" title="Memory dump">memory dump</a>. Typically, the smartphone is connected to an attacker's machine using a <a href="Universal_Serial_Bus" class="mw-redirect" title="Universal Serial Bus">USB</a> port.

Typically, Android <a href="Smartphones" class="mw-redirect" title="Smartphones">smartphones</a> securely erase encryption keys from <a href="Random-access_memory" title="Random-access memory">random-access memory</a> when the phone is locked.<a href="#cite_note-cellPhones2018-50">[50]</a> This reduces the risk of an attacker being able to retrieve the keys from memory, even if they succeeded in executing a cold boot attack against the phone.

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist reflist-columns references-column-width" style="column-width: 30em;">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFMacIver2006" class="citation conference cs1">MacIver, Douglas (2006-09-21). <a rel="nofollow" class="external text" href="http://www.secguru.com/files/hitbsecconf2006kl/DAY%202%20-%20Douglas%20MacIver%20-%20Pentesting%20BitLocker.pdf">Penetration Testing Windows Vista BitLocker Drive Encryption</a> (PDF). <a rel="nofollow" class="external text" href="http://conference.hackinthebox.org/hitbsecconf2006kl/">HITBSecConf2006, Malaysia</a>. <a href="Microsoft" title="Microsoft">Microsoft</a>. Retrieved 2008-09-23.</cite>

</li>

<li id="cite_note-halderman2008-2">^ <a href="#cite_ref-halderman2008_2-0">a</a> <a href="#cite_ref-halderman2008_2-1">b</a> <a href="#cite_ref-halderman2008_2-2">c</a> <a href="#cite_ref-halderman2008_2-3">d</a> <a href="#cite_ref-halderman2008_2-4">e</a> <a href="#cite_ref-halderman2008_2-5">f</a> <a href="#cite_ref-halderman2008_2-6">g</a> <a href="#cite_ref-halderman2008_2-7">h</a> <a href="#cite_ref-halderman2008_2-8">i</a> <a href="#cite_ref-halderman2008_2-9">j</a> <a href="#cite_ref-halderman2008_2-10">k</a> <a href="#cite_ref-halderman2008_2-11">l</a> <a href="#cite_ref-halderman2008_2-12">m</a> <cite id="CITEREFHaldermanSchoenHeningerClarkson2009" class="citation journal cs1">Halderman, J. Alex; Schoen, Seth D.; Heninger, Nadia; Clarkson, William; Paul, William; Calandrino, Joseph A.; Feldman, Ariel J.; Appelbaum, Jacob; Felten, Edward W. (2009-05-01). <a rel="nofollow" class="external text" href="https://www.usenix.org/legacy/event/sec08/tech/full_papers/halderman/halderman.pdf">"Lest we remember: cold-boot attacks on encryption keys"</a> (PDF). Communications of the ACM. 52 (5): 91–98. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F1506409.1506429">10.1145/1506409.1506429</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/0001-0782">0001-0782</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:7770695">7770695</a>.</cite>

</li>

<li id="cite_note-forensic2011-3">^ <a href="#cite_ref-forensic2011_3-0">a</a> <a href="#cite_ref-forensic2011_3-1">b</a> <a href="#cite_ref-forensic2011_3-2">c</a> <a href="#cite_ref-forensic2011_3-3">d</a> <a href="#cite_ref-forensic2011_3-4">e</a> <a href="#cite_ref-forensic2011_3-5">f</a> <a href="#cite_ref-forensic2011_3-6">g</a> <a href="#cite_ref-forensic2011_3-7">h</a> <cite id="CITEREFCarboneBeanSalois2011" class="citation conference cs1">Carbone, Richard; Bean, C; Salois, M (January 2011). <a rel="nofollow" class="external text" href="https://www.forensicfocus.com/stable/wp-content/uploads/2011/08/cold_boot_attack_for_forensiscs1.pdf">An in-depth analysis of the cold boot attack</a> (PDF). Defence Research and Development Canada.</cite>

</li>

<li id="cite_note-skorobogatov2002-4"><a href="#cite_ref-skorobogatov2002_4-0">^</a> <cite id="CITEREFSkorobogatov2002" class="citation conference cs1">Skorobogatov, Sergei (June 2002). <a rel="nofollow" class="external text" href="https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-536.pdf">Low temperature data remanence in static RAM</a> (PDF). University of Cambridge.</cite>

</li>

<li id="cite_note-bitlocker2008-5">^ <a href="#cite_ref-bitlocker2008_5-0">a</a> <a href="#cite_ref-bitlocker2008_5-1">b</a> <a href="#cite_ref-bitlocker2008_5-2">c</a> <cite id="CITEREFMacIver2008" class="citation web cs1">MacIver, Douglas (2008-02-25). <a rel="nofollow" class="external text" href="https://docs.microsoft.com/en-us/archive/blogs/si_team/protecting-bitlocker-from-cold-attacks-and-other-threats">"System Integrity Team Blog: Protecting BitLocker from Cold Attacks (and other threats)"</a>. <a href="Microsoft" title="Microsoft">Microsoft</a>. Retrieved 2020-06-24.</cite>

</li>

<li id="cite_note-memTool2008-6"><a href="#cite_ref-memTool2008_6-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20130605132146/https://citp.princeton.edu/research/memory/code/">"Memory Research Project Source Code"</a>. Center for Information Technology Policy. 2008-06-16. Archived from <a rel="nofollow" class="external text" href="https://citp.princeton.edu/research/memory/code/">the original</a> on 2013-06-05. Retrieved 2018-11-06.</cite>

</li>

<li id="cite_note-7"><a href="#cite_ref-7">^</a> <cite class="citation pressrelease cs1"><a rel="nofollow" class="external text" href="http://www.prnewswire.com/news-releases/passware-software-cracks-bitlocker-encryption-open-78212917.html">"Passware Software Cracks BitLocker Encryption Open"</a> (Press release). PR Newswire. 2009-12-01.</cite>

</li>

<li id="cite_note-hargreaves2008-8"><a href="#cite_ref-hargreaves2008_8-0">^</a> <cite id="CITEREFHargreavesChivers2008" class="citation conference cs1">Hargreaves, C.; Chivers, H. (March 2008). <a rel="nofollow" class="external text" href="https://www.researchgate.net/publication/221548532">"Recovery of Encryption Keys from Memory Using a Linear Scan"</a>. 2008 Third International Conference on Availability, Reliability and Security. 2008 Third International Conference on Availability, Reliability and Security. pp. 1369–1376. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FARES.2008.109">10.1109/ARES.2008.109</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-7695-3102-1</bdi>.</cite>

</li>

<li id="cite_note-carbone2011-9"><a href="#cite_ref-carbone2011_9-0">^</a> <cite id="CITEREFCarboneBeanSalois2011" class="citation web cs1">Carbone, R.; Bean, C; Salois, M. (January 2011). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20130408131959/http://www.dtic.mil/cgi-bin/GetTRDoc?AD=ADA545078">"An In-depth Analysis of the Cold Boot Attack: Can it be Used for Sound Forensic Memory Acquisition?"</a>. Defense Technical Information Center. Archived from <a rel="nofollow" class="external text" href="http://www.dtic.mil/cgi-bin/GetTRDoc?AD=ADA545078">the original</a> (pdf) on April 8, 2013.</cite>

</li>

<li id="cite_note-gruhn2016-10">^ <a href="#cite_ref-gruhn2016_10-0">a</a> <a href="#cite_ref-gruhn2016_10-1">b</a> <cite id="CITEREFGruhn2016" class="citation web cs1">Gruhn, Michael (2016-11-24). <a rel="nofollow" class="external text" href="https://d-nb.info/1122350279/34">"Forensically Sound Data Acquisition in the age of Anti-Forensic Innocence"</a>. Erlangen, Germany: Friedrich-Alexander-Universität Erlangen-Nürnberg.</cite>

</li>

<li id="cite_note-bitlockerOverview2008-11"><a href="#cite_ref-bitlockerOverview2008_11-0">^</a> <cite id="CITEREFBitlocker_Technical_Overview,_2008" class="citation web cs1"><a rel="nofollow" class="external text" href="https://technet.microsoft.com/en-us/library/cc732774.aspx">"BitLocker Drive Encryption Technical Overview"</a>. <a href="Microsoft" title="Microsoft">Microsoft</a>. 2008. Retrieved 2008-11-19.</cite>

</li>

<li id="cite_note-tresor-usenix-12">^ <a href="#cite_ref-tresor-usenix_12-0">a</a> <a href="#cite_ref-tresor-usenix_12-1">b</a> <a href="#cite_ref-tresor-usenix_12-2">c</a> <a rel="nofollow" class="external text" href="http://www1.informatik.uni-erlangen.de/tresorfiles/tresor.pdf">TRESOR USENIX paper, 2011</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20120113062139/http://www1.informatik.uni-erlangen.de/tresorfiles/tresor.pdf">Archived</a> 2012-01-13 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>

</li>

<li id="cite_note-loopamnesia-acsac-13"><a href="#cite_ref-loopamnesia-acsac_13-0">^</a> <cite id="CITEREFSimmons2011" class="citation conference cs1">Simmons, Patrick (2011-12-05). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20181106132326/https://www.ideals.illinois.edu/bitstream/handle/2142/18862/amnesia.pdf?sequence=2&isAllowed=y">Security through amnesia: a software-based solution to the cold boot attack on disk encryption</a> (PDF). Proceedings of the 27th Annual Computer Security Applications Conference. ACM. pp. 73–82. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F2076732.2076743">10.1145/2076732.2076743</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4503-0672-0</bdi>. Archived from <a rel="nofollow" class="external text" href="https://www.ideals.illinois.edu/bitstream/handle/2142/18862/amnesia.pdf?sequence=2&isAllowed=y">the original</a> (PDF) on 2018-11-06. Retrieved 2018-11-06.</cite>

</li>

<li id="cite_note-muller2010-14"><a href="#cite_ref-muller2010_14-0">^</a> <cite id="CITEREFMüller2010" class="citation web cs1">Müller, Tilo (2010-05-31). <a rel="nofollow" class="external text" href="https://faui1-files.cs.fau.de/filepool/thesis/diplomarbeit-2010-mueller.pdf">"Cold-Boot Resistant Implementation of AES in the Linux Kernel"</a> (PDF). Aachen, Germany: RWTH Aachen University.</cite>

</li>

<li id="cite_note-tresorBlog-15"><a href="#cite_ref-tresorBlog_15-0">^</a> <cite id="CITEREFFriedrich-Alexander-Universität_Erlangen-Nürnberg" class="citation web cs1">Friedrich-Alexander-Universität Erlangen-Nürnberg. <a rel="nofollow" class="external text" href="https://www.cs1.tf.fau.de/research/system-security-and-software-protection-group/tresor-trevisor-armored/">"Tresor / TreVisor / Armored: TRESOR Runs Encryption Securely Outside RAM / The TRESOR Hypervisor / for Android-driven Devices"</a>. Retrieved 2018-11-06.</cite>

</li>

<li id="cite_note-tews2010-16"><a href="#cite_ref-tews2010_16-0">^</a> <cite id="CITEREFTews2010" class="citation conference cs1">Tews, Erik (December 2010). <a rel="nofollow" class="external text" href="https://events.ccc.de/2010/12/28/frozen-cache/">FrozenCache – Mitigating cold-boot attacks for Full-Disk-Encryption software</a>. 27th Chaos Communication.</cite>

</li>

<li id="cite_note-frozencache-17"><a href="#cite_ref-frozencache_17-0">^</a> <a rel="nofollow" class="external text" href="http://frozencache.blogspot.com/">Frozen Cache Blog</a>

</li>

<li id="cite_note-copker-18"><a href="#cite_ref-copker_18-0">^</a> <cite id="CITEREFGuanLinLuoJing2014" class="citation conference cs1">Guan, Le; Lin, Jingqiang; Luo, Bo; Jing, Jiwu (February 2014). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20160803150133/http://www.internetsociety.org/sites/default/files/07_1_1.pdf">Copker: Computing with Private Keys without RAM</a> (PDF). 21st ISOC Network and Distributed System Security Symposium (NDSS). Archived from <a rel="nofollow" class="external text" href="https://www.internetsociety.org/sites/default/files/07_1_1.pdf">the original</a> (PDF) on 2016-08-03. Retrieved 2016-03-01.</cite>

</li>

<li id="cite_note-guan2015-19"><a href="#cite_ref-guan2015_19-0">^</a> <cite id="CITEREFGuanLinLuoJing2015" class="citation conference cs1">Guan, L.; Lin, J.; Luo, B.; Jing, J.; Wang, J. (May 2015). <a rel="nofollow" class="external text" href="https://www.ieee-security.org/TC/SP2015/papers-archived/6949a003.pdf">"Protecting Private Keys against Memory Disclosure Attacks Using Hardware Transactional Memory"</a> (PDF). 2015 IEEE Symposium on Security and Privacy. 2015 IEEE Symposium on Security and Privacy. pp. 3–19. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FSP.2015.8">10.1109/SP.2015.8</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4673-6949-7</bdi>.</cite>

</li>

<li id="cite_note-dean2009-20"><a href="#cite_ref-dean2009_20-0">^</a> <cite id="CITEREFDean2009" class="citation news cs1">Dean, Sarah (2009-11-11). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20120915080532/http://www.freeotfe.org/docs/Main/FAQ.htm#de">"Cold Boot Attacks on Encryption Keys (aka "DRAM attacks")"</a>. Archived from <a rel="nofollow" class="external text" href="http://www.freeotfe.org/docs/Main/FAQ.htm#de">the original</a> on 2012-09-15. Retrieved 2008-11-11.</cite>

</li>

<li id="cite_note-wired2008-21"><a href="#cite_ref-wired2008_21-0">^</a> <cite id="CITEREFWired,_2008" class="citation magazine cs1"><a rel="nofollow" class="external text" href="http://blog.wired.com/27bstroke6/2008/02/encryption-stil.html">"Encryption Still Good; Sleeping Mode Not So Much, PGP Says"</a>. <a href="Wired_(magazine)" title="Wired (magazine)">Wired</a>. 2008-02-21. Retrieved 2008-02-22.</cite>

</li>

<li id="cite_note-weis-22"><a href="#cite_ref-weis_22-0">^</a> <cite id="CITEREFWeisPrivateCore2014" class="citation conference cs1">Weis S, PrivateCore (2014-06-25). <a rel="nofollow" class="external text" href="https://www.blackhat.com/docs/us-14/materials/us-14-Weis-Protecting-Data-In-Use-From-Firmware-And-Physical-Attacks-WP.pdf#page=2">Protecting Data In-Use from Firmware and Physical Attacks</a> (PDF). <a rel="nofollow" class="external text" href="https://www.blackhat.com/us-14/archives.html#Weis">Black Hat USA 2014</a>. Palo Alto, California, U. S. A. p. 2.</cite>

</li>

<li id="cite_note-23"><a href="#cite_ref-23">^</a> B. Huang <a rel="nofollow" class="external text" href="http://web.mit.edu/bunnie/www/proj/anatak/AIM-2002-008.pdf">"Keeping Secrets in Hardware: The Microsoft Xbox Case Study"</a>, "CHES 2002 Lecture Notes in Notes in Computer Science Volume 2523", 2003

</li>

<li id="cite_note-ramCrypt2016-24">^ <a href="#cite_ref-ramCrypt2016_24-0">a</a> <a href="#cite_ref-ramCrypt2016_24-1">b</a> <cite id="CITEREFGötzfriedMüllerDrescherNürnberger2016" class="citation conference cs1">Götzfried, Johannes; Müller, Tilo; Drescher, Gabor; Nürnberger, Stefan; Backes, Michael (2016). <a rel="nofollow" class="external text" href="https://faui1-files.cs.fau.de/filepool/projects/ramcrypt/ramcrypt.pdf">"RamCrypt: Kernel-based Address Space Encryption for User-mode Processes"</a> (PDF). Proceedings of the 11th ACM on Asia Conference on Computer and Communications Security. ASIA CCS '16. New York, NY, USA: ACM. pp. 919–924. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F2897845.2897924">10.1145/2897845.2897924</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4503-4233-9</bdi>. Retrieved 2018-11-07.</cite>

</li>

<li id="cite_note-25"><a href="#cite_ref-25">^</a> Y. Hu, G. Hammouri, and B. Sunar <a rel="nofollow" class="external text" href="http://dl.acm.org/citation.cfm?id=1456461">"A fast real-time memory authentication protocol"</a>, "STC '08 Proceedings of the 3rd ACM workshop on Scalable trusted computing", 2008

</li>

<li id="cite_note-26"><a href="#cite_ref-26">^</a> G. Duc and R. Keryell, <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=4041192">"CryptoPage: an efficient secure architecture with memory encryption, integrity and information leakage protection"</a>, Dec. 2006

</li>

<li id="cite_note-27"><a href="#cite_ref-27">^</a> X. Chen, R. P. Dick, and A. Choudhary <a rel="nofollow" class="external text" href="http://dl.acm.org/citation.cfm?id=1403657,">"Operating system controlled processor-memory bus encryption"</a>, "Proceedings of the conference on Design, automation and test in Europe", 2008

</li>

<li id="cite_note-28"><a href="#cite_ref-28">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.veracrypt.fr/en/Release%20Notes.html">"VeraCrypt Release Notes"</a>.</cite>

</li>

<li id="cite_note-29"><a href="#cite_ref-29">^</a> M. Henson and S. Taylor <a rel="nofollow" class="external text" href="http://dl.acm.org/citation.cfm?id=2524549">"Beyond full disk encryption:protection on security-enhanced commodity processors"</a>, "Proceedings of the 11th international conference on applied cryptography and network security", 2013

</li>

<li id="cite_note-30"><a href="#cite_ref-30">^</a> M. Henson and S. Taylor <a rel="nofollow" class="external text" href="http://dl.acm.org/citation.cfm?id=2566673">"Memory encryption: a survey of existing techniques"</a>, "ACM Computing Surveys volume 46 issue 4", 2014

</li>

<li id="cite_note-31"><a href="#cite_ref-31">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.trustedcomputinggroup.org/resources/pc_client_work_group_platform_reset_attack_mitigation_specification_version_10/">"TCG Platform Reset Attack Mitigation Specification"</a>. <a href="Trusted_Computing_Group" title="Trusted Computing Group">Trusted Computing Group</a>. May 28, 2008. Retrieved June 10, 2009.</cite>

</li>

<li id="cite_note-32"><a href="#cite_ref-32">^</a> <cite id="CITEREFTeague2017" class="citation journal cs1">Teague, Ryne (2017). "EVIDENCE VERIFICATION COMPLICATIONS WITH SOLID-STATE DRIVES". Association of Digital Forensics, Security and Law. 12: 75–85.</cite>

</li>

<li id="cite_note-tails-33"><a href="#cite_ref-tails_33-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://tails.boum.org/doc/advanced_topics/cold_boot_attacks/index.en.html">"Tails - Protection against cold boot attacks"</a>. Retrieved 7 November 2018.</cite>

</li>

<li id="cite_note-34"><a href="#cite_ref-34">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://redmine.tails.boum.org/code/issues/5356">"Erase video memory on shutdown (#5356) · Issues · tails / Tails · GitLab"</a>.</cite>

</li>

<li id="cite_note-35"><a href="#cite_ref-35">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://hsmr.cc/palinopsia/">"The Palinopsia Bug"</a>. hsmr.cc. 2022-04-17. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20220224224922/https://hsmr.cc/palinopsia/">Archived</a> from the original on 2022-02-24. Retrieved 2022-04-17.</cite>

</li>

<li id="cite_note-36"><a href="#cite_ref-36">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://2019.www.torproject.org/docs/onion-services.html.en">"Tor: Onion Service Protocol"</a>. 2019.www.torproject.org. 2022-04-17. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20220405071524/https://2019.www.torproject.org/docs/onion-services.html.en">Archived</a> from the original on 2022-04-05. Retrieved 2022-04-17.</cite>

</li>

<li id="cite_note-37"><a href="#cite_ref-37">^</a> <a rel="nofollow" class="external free" href="https://svn-archive.torproject.org/svn/projects/design-paper/tor-design.pdf">https://svn-archive.torproject.org/svn/projects/design-paper/tor-design.pdf</a>

</li>

<li id="cite_note-38"><a href="#cite_ref-38">^</a> <cite id="CITEREFIgor_Skochinsky2014" class="citation web cs1">Igor Skochinsky (2014-03-12). <a rel="nofollow" class="external text" href="https://www.slideshare.net/codeblue_jp/igor-skochinsky-enpub">"Secret of Intel Management Engine"</a>. SlideShare. pp. 26–29. Retrieved 2014-07-13.</cite>

</li>

<li id="cite_note-39"><a href="#cite_ref-39">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/2nd-gen-core-desktop-vol-1-datasheet.pdf">"2nd Generation Intel Core Processor Family Desktop, Intel Pentium Processor Family Desktop, and Intel Celeron Processor Family Desktop"</a> (PDF). June 2013. p. 23. Retrieved 2015-11-03.</cite>

</li>

<li id="cite_note-40"><a href="#cite_ref-40">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/2nd-gen-core-family-mobile-vol-1-datasheet.pdf">"2nd Generation Intel Core Processor Family Mobile and Intel Celeron Processor Family Mobile"</a> (PDF). September 2012. p. 24. Retrieved 2015-11-03.</cite>

</li>

<li id="cite_note-41"><a href="#cite_ref-41">^</a> <cite id="CITEREFMichael_Gruhn,_Tilo_Muller" class="citation web cs1">Michael Gruhn, Tilo Muller. <a rel="nofollow" class="external text" href="https://www1.cs.fau.de/filepool/projects/coldboot/fares_coldboot.pdf">"On the Practicability of Cold Boot Attacks"</a> (PDF). Retrieved 2018-07-28.</cite>

</li>

<li id="cite_note-42"><a href="#cite_ref-42">^</a> <cite id="CITEREFJohannes_BauerMichael_GruhnFelix_C._Freiling2016" class="citation journal cs1">Johannes Bauer; Michael Gruhn; Felix C. Freiling (2016). <a rel="nofollow" class="external text" href="https://doi.org/10.1016%2Fj.diin.2016.01.009">"Lest we forget: Cold-boot attacks on scrambled DDR3 memory"</a>. Digital Investigation. 16: S65 – S74. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1016%2Fj.diin.2016.01.009">10.1016/j.diin.2016.01.009</a>.</cite>

</li>

<li id="cite_note-43"><a href="#cite_ref-43">^</a> <cite id="CITEREFSalessawi_FeredeYitbarek_MisikerTadesse_Aga" class="citation web cs1">Salessawi Ferede; Yitbarek Misiker; Tadesse Aga. <a rel="nofollow" class="external text" href="https://web.eecs.umich.edu/~taustin/papers/HPCA17-coldboot.pdf">"Cold Boot Attacks are Still Hot: Security Analysis of Memory Scramblers in Modern Processors"</a> (PDF). Retrieved 2018-07-28.</cite>

</li>

<li id="cite_note-microsoftBios2018-44"><a href="#cite_ref-microsoftBios2018_44-0">^</a> <cite id="CITEREFkpacquer2018" class="citation web cs1">kpacquer (2018-05-14). <a rel="nofollow" class="external text" href="https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/boot-to-uefi-mode-or-legacy-bios-mode">"Boot to UEFI Mode or Legacy BIOS mode"</a>. Microsoft. Retrieved 2018-11-06.</cite>

</li>

<li id="cite_note-biosKeys-45"><a href="#cite_ref-biosKeys_45-0">^</a> <cite id="CITEREFS2015" class="citation cs2">S, Ray (2015-12-08), <a rel="nofollow" class="external text" href="https://kb.wisc.edu/page.php?id=58779">Booting to the Boot Menu and BIOS</a>, University of Wisconsin-Madison, retrieved 2018-11-06</cite>

</li>

<li id="cite_note-dell-46"><a href="#cite_ref-dell_46-0">^</a> <cite id="CITEREFDell_Inc.2018" class="citation web cs1">Dell Inc. (2018-10-09). <a rel="nofollow" class="external text" href="https://www.dell.com/support/article/au/en/aubsdt1/sln284985/how-to-perform-a-bios-or-cmos-reset-and-or-clear-the-nvram-on-your-dell-system">"How to Perform a BIOS or CMOS Reset and/or Clear the NVRAM on your Dell System | Dell Australia"</a>. Dell Support.</cite>

</li>

<li id="cite_note-47"><a href="#cite_ref-47">^</a> <cite id="CITEREFRuud2014" class="citation cs2">Ruud, Schramp (2014-06-13), <a rel="nofollow" class="external text" href="https://www.youtube.com/watch?v=i_WvtO1NIsA">OHM2013: RAM Memory acquisition using live-BIOS modification</a>, <a rel="nofollow" class="external text" href="https://ghostarchive.org/varchive/youtube/20211221/i_WvtO1NIsA">archived</a> from the original on 2021-12-21, retrieved 2018-07-28</cite>

</li>

<li id="cite_note-48"><a href="#cite_ref-48">^</a> <cite id="CITEREFMichael2016" class="citation thesis cs1">Michael, Gruhn (2016). <a rel="nofollow" class="external text" href="http://nbn-resolving.de/urn:nbn:de:bvb:29-opus4-79386">Forensically Sound Data Acquisition in the Age of Anti-Forensic Innocence</a> (Thesis). Friedrich-Alexander-Universität Erlangen-Nürnberg (FAU). p. 67.</cite>

</li>

<li id="cite_note-49"><a href="#cite_ref-49">^</a> <cite id="CITEREFSchramp2017" class="citation journal cs1">Schramp, R. (March 2017). "Live transportation and RAM acquisition proficiency test". Digital Investigation. 20: 44–53. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1016%2Fj.diin.2017.02.006">10.1016/j.diin.2017.02.006</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/1742-2876">1742-2876</a>.</cite>

</li>

<li id="cite_note-cellPhones2018-50">^ <a href="#cite_ref-cellPhones2018_50-0">a</a> <a href="#cite_ref-cellPhones2018_50-1">b</a> <a href="#cite_ref-cellPhones2018_50-2">c</a> <cite id="CITEREFBali2018" class="citation book cs1">Bali, Ranbir Singh (July 2018). <a rel="nofollow" class="external text" href="https://www.researchgate.net/publication/326211565">Cold Boot Attack on Cell Phones</a>. Concordia University of Edmonton.</cite><code class="cs1-code">{{cite book}}</code>: CS1 maint: location missing publisher (link)

</li>

</ol></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<ul><li><a rel="nofollow" class="external text" href="https://www.youtube.com/watch?v=JDaicPIgn9U">Lest We Remember: Cold Boot Attacks on Encryption Keys</a> on <a href="YouTube_video_(identifier)" class="mw-redirect" title="YouTube video (identifier)">YouTube</a></li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20080516212552/http://mcgrewsecurity.com/projects/msramdmp/">McGrew Security's Proof of Concept</a></li>

<li><a rel="nofollow" class="external text" href="https://www.theregister.co.uk/2013/02/16/frost_android_encryption_crack/">Boffins Freeze Phone to Crack Android On-Device Crypto</a></li>

<li><cite id="CITEREFSkorobogatov2002" class="citation journal cs1">Skorobogatov, Sergei (June 2002). <a rel="nofollow" class="external text" href="http://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-536.html">"Low temperature data remanence in static RAM"</a>. <a href="University_of_Cambridge" title="University of Cambridge">University of Cambridge</a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.48456%2Ftr-536">10.48456/tr-536</a>. Retrieved 2008-02-27.</cite></li></ul></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-07-14" href="https://en.wikipedia.org/wiki/?title=Cold_boot_attack&oldid=1300523330">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>